Motivation

• apply the suggestion that perf: avoid large offset query via limit windowing #180 has taken before being merged.
• for snapshoted event, use full-size window query to fetch the first sequence version.
• integration test for limitWindowsing.

it also fixed the test failed after #180 merged.

Explan

In the normal case...(the sequence version always start from 1)

Query pid = test-account-1, from = 1, to = 501, batch-size= 500
Query pid = test-account-1, from = 501, to = 1001, batch-size= 500
Query pid = test-account-1, from = 1001, to = 1501, batch-size= 500
Query pid = test-account-1, total = 1000

After the snapshot, the existing sequence version may start from 1000 or higher.(or something happened unexpectedly, like the migrator test)(the persistenceActor It will not be affected, because the Reply will query HigherSequenceNumber in advance, but queries such as currentEventsByPersistenceId can not be required)
In this case we should use full windows for the first query only.

- Query pid = test-account-1, from = 1, to = 501, batch-size= 500
+ Query pid = test-account-1, from = 1, to = 9223372036854775807, batch-size= 500
Query pid = test-account-1, from = 1501, to = 2001, batch-size= 500
Query pid = test-account-1, from = 2001, to = 2501, batch-size= 500
Query pid = test-account-1, total = 1000